chore: update vitest to support vite v6 #1108
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vite was updated from v5 to v6, and vitest needs to be updated to match. vitest 2.2 added and then removed the support; 3.0 will add it but is still in beta until January. Signed-off-by: Tim deBoer <[email protected]>
|
Failing 1 test, can confirm it's working fine though / able to do all the features from the looks of it via testing. Should we disable the test + open up an issue to fix it so we can merge the other two PR's as well for the release? @deboer-tim |
|
Closing / replaced by #1116 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Vite was updated from v5 to v6, and vitest needs to be updated to match. vitest 2.2 added and then removed the support; 3.0 will add it but is still in beta until January.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
Fixes #1107.
How to test this PR?
PR checks are enough.